Method of providing call control information from a mobile phone to a peripheral device

ABSTRACT

The systems, methods, and devices of the various embodiments provide call control information from a mobile phone to another device by moving the functionality enabling the separation of call control commands from audio data off the mobile phone. The various embodiments handle the separation of call control commands from audio data at an ear piece or other peripheral device, such as a personal hub, which is part of a multiple subscriber device system. The various embodiments enable the standard Bluetooth® Hands-Free Profile to be used by a multiple subscriber device system to interact with a mobile phone.

BACKGROUND

Mobile phones offer significant capabilities of interest to users, but auser must physically interact with the mobile phone to navigate menus,make calls, or listen to messages. This physical interaction may bedistracting, cumbersome, and intrusive. To reduce the need for physicalinteraction, an additional wireless device, such as an ear piece orother peripheral device (e.g., a personal hub), may be linked with themobile phone, such as via a Bluetooth® link. The ear piece or otherperipheral device may be configured to exchange audio data and callcontrol information (e.g., attention (“AT”) commands) with the mobilephone. In this manner, the ability of a user to control the operation ofthe mobile phone via the ear piece or other peripheral device may reducethe distraction, intrusiveness, and burden associated with physicalinteraction with the mobile phone.

However, mobile phones using the standard Bluetooth® Hands-Free Profile(i.e., Hands-Free Profile 1.6 specification published by the Bluetooth®Special Interest Group, May 10, 2011, available atwww.bluetooth.org/Technical/Specifications/adopted.htm, hereinincorporated by reference in its entirety) can only support a singlesubscriber device using the Hands-Free Profile at one time. The standardBluetooth® Hands-Free Profile will not allow a mobile phone to exchangeaudio data with a first communication device and call control commandswith a second communication device. Only one Hands-Free Profile devicemay be connected to the mobile phone at a time to exchange call controlcommands and/or audio data. Therefore, without additional modifications(e.g., additional software on the mobile phone), mobile phones using thestandard Bluetooth® Hands-Free Profile cannot support multiplesubscriber device systems (i.e., personal hub systems including apersonal hub and at least one ear piece).

Previous multiple subscriber device systems have required additionalsoftware resident on the mobile phone to convey information to thesecond communication device using out of band signaling (i.e.,non-Bluetooth® Hands-Free Profile established links). While potentiallya solution to the limitations of the Bluetooth® Hands-Free Profile, thesoftware based out of band signaling approach requires software to bedeveloped for each phone platform (e.g., Android®, iOS®, RIM®, etc) atsignificant cost. Additionally, changes, such as updates, to theoperating system of a platform may alter the call handling on theplatform and require additional modifications to the out of bandsignaling software. To ensure functionality, multiple versions of theout of band signaling software may be needed for each platform.

SUMMARY

The systems, methods, and devices of the various embodiments providecall control information from a mobile phone to another device by movingthe functionality enabling the separation of call control commands fromaudio data off the mobile phone. The various embodiments handle theseparation of call control commands from audio data at an ear piece orother peripheral device, such as a personal hub, which is part of amultiple subscriber device system. The various embodiments enable thestandard Bluetooth® Hands-Free Profile to be used by a multiplesubscriber device system to interact with a mobile phone.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and constitutepart of this specification, illustrate exemplary embodiments of theinvention, and together with the general description given above and thedetailed description given below, serve to explain the features of theinvention.

FIG. 1 is a communication system block diagram of a multiple subscriberdevice system suitable for use with the various embodiments.

FIG. 2 is a communication flow diagram illustrating radio link exchangesin a multiple subscriber device system according to an embodiment.

FIG. 3 is a communication flow diagram illustrating radio link exchangesin a multiple subscriber device system according to a second embodiment.

FIG. 4. is a communication flow diagram illustrating radio linkexchanges in a multiple subscriber device system according to a thirdembodiment.

FIG. 5 is a process flow diagram illustrating an embodiment method forproviding call control information from a mobile phone to anotherdevice.

FIG. 6 is a process flow diagram illustrating a second embodiment methodfor providing call control information from a mobile phone to anotherdevice.

FIG. 7 is a process flow diagram illustrating a third embodiment methodfor providing call control information from a mobile phone to anotherdevice.

FIG. 8 is a component diagram of an example personal hub suitable foruse with the various embodiments.

FIG. 9 is a component diagram of an example mobile device suitable foruse with the various embodiments.

FIGS. 10A and 10B are component diagrams of example wireless earpiecessuitable for use with the various embodiments.

DETAILED DESCRIPTION

The various embodiments will be described in detail with reference tothe accompanying drawings. Wherever possible, the same reference numberswill be used throughout the drawings to refer to the same or like parts.References made to particular examples and implementations are forillustrative purposes, and are not intended to limit the scope of theinvention or the claims.

The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any implementation described herein as“exemplary” is not necessarily to be construed as preferred oradvantageous over other implementations.

As used herein, the terms “mobile device,” “mobile phone,” and “receiverdevice” are used interchangeably herein to refer to any one or all ofcellular telephones, smart phones, personal or mobile multi-mediaplayers, personal data assistants (PDA's), laptop computers, tabletcomputers, smart books, palm-top computers, wireless electronic mailreceivers, multimedia Internet enabled cellular telephones, wirelessgaming controllers, and similar personal electronic devices whichinclude a programmable processor and memory and circuitry for receivingphone calls, sending and receiving audio data, and sending and receivingcall control commands.

As used herein, the term “personal hub” is used herein to refer to anydevice that may be worn or carried by a user and may interact with avariety of mobile devices and/or earpieces. In an embodiment, a personalhub may be configured to be worn by a user around the user's wrist in amanner similar to that of a wrist watch. In alternative embodiments, apersonal hub may be a badge, tag, bracelet, patch, belt buckle,medallion, pen, key chain, or any other device worn or carried by auser. In an embodiment, a personal hub may wirelessly communicate with auser's mobile device(s), such as a smart phone, and a wireless earpieceworn by the user. The personal hub may wirelessly communicate with theuser's mobile device(s) to enable the user to operate the user's mobiledevice(s) remotely. In an embodiment, a personal hub system may be amulti-subscriber device system including a personal hub and one or twowireless earpieces worn by the user, together enabling a personal hubsystem user to utilize a user's mobile device(s) remotely.

Mobile phones offer significant capabilities of interest to users, but auser must physically interact with the mobile phone to navigate menus,make calls, or listen to messages. This physical interaction may bedistracting, cumbersome, and intrusive. To reduce the need for physicalinteraction, an additional wireless device, such as an ear piece orother peripheral device (e.g., a personal hub), may be linked with themobile phone, such as via a Bluetooth® link. The ear piece or otherperipheral device may be configured to exchange audio data and callcontrol information (e.g., attention (“AT”) commands) with the mobilephone. In this manner, the ability of a user to control the operation ofthe mobile phone via the ear piece or other peripheral device may reducethe distraction, intrusiveness, and burden associated with physicalinteraction with the mobile phone.

However, mobile phones using the standard Bluetooth® Hands-Free Profile(i.e., Hands-Free Profile 1.6 specification published by the Bluetooth®Special Interest Group, herein incorporated by reference in itsentirety) can only support a single subscriber device using theHands-Free Profile at one time. The standard Bluetooth® Hands-FreeProfile will not allow a mobile phone to exchange audio data with afirst communication device and call control commands with a secondcommunication device. Only one Hands-Free Profile device may beconnected to the mobile phone at a time to exchange call controlcommands and/or audio data. Therefore, without additional modifications(e.g., additional software on the mobile phone), mobile phones using thestandard Bluetooth® Hands-Free Profile cannot support multiplesubscriber device systems (i.e., personal hub systems including apersonal hub and at least one ear piece).

Previous multiple subscriber device systems, such as the personal hubsystem described in U.S. Pat. No. 7,996,571, have required additionalsoftware resident on the mobile phone to convey information to thesecond communication device using out of band signaling (i.e.,non-Bluetooth® Hands-Free Profile established links). The personal hubsystem described in U.S. Pat. No. 7,996,571 uses physical layerapplications and software/hardware on the mobile device, such as theadmission controller 312 and dual-mode manager 314, to separate callcontrol commands from call audio. See e.g., col. 8, line 26 through col.9, line 30; col. 12, lines 28 through col. 13, line 25; and FIG. 7.

While potentially a solution to the limitations of the Bluetooth®Hands-Free Profile, the software based out of band signaling approachrequires software to be developed for each phone platform (e.g.,Android®, iOS®, RIM®, etc) at significant cost. Additionally, changes,such as updates, to the operating system of a platform may alter thecall handling on the platform and require additional modifications tothe out of band signaling software. To ensure functionality, multipleversions of the out of band signaling software may be needed for eachplatform.

The systems, methods, and devices of the various embodiments leveragethe existing capabilities of the standard Bluetooth® Hands-Free Profilewithout requiring additional software to interact with the mobilephone's call handling system to manage calls on the mobile phone. Thevarious embodiments solve the problems with developing and updatingsoftware for multiple subscriber device system (e.g., personal hubsystem including a personal hub and at least one ear piece) for eachmobile phone platform. The various embodiments move the functionalityenabling the separation of call control commands from audio data off themobile phone. The various embodiments handle separation of call controlcommands from audio data at an ear piece or other peripheral device,such as a personal hub, which is part of the multiple subscriber devicesystem. In this manner, the various embodiments enable the standardBluetooth® Hands-Free Profile to be used by a multiple subscriber devicesystem to interact with the mobile phone, rather than requiringadditional software to be downloaded to the mobile phone.

In overview, the various embodiments manage calls by providing callcontrol information from a mobile phone to a peripheral device (e.g., apersonal hub) by establishing a first Bluetooth® link with a firstcommunication device (e.g., an ear piece). As used herein, “call controlinformation” means that data which is carried over AT commands andresponses in the Service Level Connection of the Bluetooth® HandsFreeProfile, and includes but is not limited to, answering and placingcalls, call termination, incoming call alerts including Calling LineIdentification, and status information related to call setup and callprogress. In an embodiment, the mobile phone and first communicationdevice may exchange call control commands and audio data over the firstBluetooth® link. The first communication device may establish a separatesecond Bluetooth® link with the peripheral device, and the firstcommunication device and the peripheral device may exchange call controlcommands over the second Bluetooth® link. In this manner, the singlelink supported in the standard Bluetooth® Hands-Free Profile may enablethe exchange of call control commands between the mobile phone, firstcommunication device, and peripheral device enabling the peripheraldevice to control call establishment on the mobile phone.

In an embodiment, a first standard Bluetooth® link as defined by theBluetooth® Hands-Free Profile, including both a service level connection(i.e., a call control connection) for exchanging call control commandsand an audio connection for exchanging audio data, may be establishedbetween a mobile phone and an ear piece. As used herein, an “out of bandlink” is used to refer to a radio link not established according to theBluetooth® Hands-Free Profile. In an embodiment, an out of band link(e.g., a separate Bluetooth® link, Peanut, Wi-Fi, ANT+, etc. notestablished according to the Bluetooth® Hands-Free Profile) may beestablished between the ear piece and a peripheral device (e.g.,personal hub). Call control commands may be sent from the mobile phoneto the ear piece via the service level connection over the firstBluetooth® link. The ear piece may receive the call control commands andrelay them to the peripheral device via the out of band link. Theperipheral device may take an action based on the call control commandsand/or generate its own call control commands Call control commandsgenerated by the peripheral device (e.g., an answer command) may be sentto the ear piece via the out of band link. The ear piece may receive thecall control commands and relay them to the mobile phone via the servicelevel connection over the first Bluetooth® link. Audio data may beexchanged between the mobile phone and the ear piece via the audioconnection over the first Bluetooth® link, but the audio data may not berelayed to the peripheral device. In this manner, the ear piece mayhandle audio data independent of call control commands In a furtherembodiment, the peripheral device may also establish a second out ofband link (e.g., Bluetooth® SPP, Wi-Fi, etc.) with the mobile phone torequest and/or receive phone book information from the mobile phoneand/or phone book information from the mobile phone may be requestedand/or received via the Bluetooth® Phone Book Access Profile ifavailable/supported by the mobile phone.

In another embodiment, a first standard Bluetooth® link as defined bythe Bluetooth® Hands-Free Profile, including both a service levelconnection (i.e., a call control connection) for exchanging call controlcommands and an audio connection for exchanging audio data, may beestablished between a mobile phone and an ear piece. A first out of bandlink (e.g., a separate Bluetooth® link, Peanut, WiFi, ANT+, etc. notestablished according to the Bluetooth® Hands-Free Profile) may beestablished between the ear piece and the mobile phone. The mobile phonemay run a relay application which may establish a second out of bandlink (e.g., a separate Bluetooth® link, Peanut, Wi-Fi, ANT+, etc. notestablished according to the Bluetooth® Hands-Free Profile) between themobile phone and a peripheral device. Call control commands may be sentfrom the mobile phone to the ear piece via the service level connectionover the first Bluetooth® link. The ear piece may receive the callcontrol commands and relay them back to the relay application on themobile phone via the first out of band link. The relay application mayreceive the call control commands and send them to the peripheral devicevia the second out of band link. The peripheral device may take anaction based on the call control commands and/or generate its own callcontrol commands Call control commands generated by the peripheraldevice (e.g., an answer command) may be sent to the relay application onthe mobile phone via the second out of band link. The relay applicationmay receive the call control commands and send them to the ear piece viathe first out of band link. The ear piece may receive the call controlcommands and relay them to the mobile phone via the service levelconnection over the first Bluetooth® link. Audio data may be exchangedbetween the mobile phone and the ear piece via the audio connection overthe first Bluetooth® link, but the audio data may not be relayed to themobile phone via the first out of band link. In this manner, the earpiece may handle audio data independent of call control commands.Additionally, even though a relay application may be present on themobile device, the relay application need only interact with the earpiece and peripheral device via the out of band links. Thus the relayapplication does not need to interact with the Bluetooth® Hands-FreeProfile or other call handling systems on the mobile phone. In thismanner, the relay application may not need to be tailored to each mobilephone platform and/or call handling system.

In an embodiment, a first standard Bluetooth® link as defined by theBluetooth® Hands-Free Profile, including both a service level connection(i.e., a call control connection) for exchanging call control commandsand an audio connection for exchanging audio data, may be establishedbetween a mobile phone and a peripheral device. In this manner, theperipheral device may be registered with the mobile device according tothe Bluetooth® Hands-Free Profile as a hands free device. A secondstandard Bluetooth® link as defined by the Bluetooth® Hands-FreeProfile, including both a service level connection (i.e., a call controlconnection) for exchanging call control commands and an audio connectionfor exchanging audio data, may be established between the peripheraldevice and the ear piece. In this manner, the ear piece may beregistered with the peripheral device according to the Bluetooth®Hands-Free Profile as a hands free device. The registration of the earpiece with the peripheral device via the Bluetooth® Hands-Free Profilemay enable any Bluetooth® enabled ear piece to be used with the multiplesubscriber device system. The peripheral device may be configured to acton and/or generate call control commands, and the peripheral device mayrelay audio data and/or call control commands between the mobile phoneand ear piece as well. In an embodiment, the peripheral device maymodify the call control commands received from the mobile phone beforerelaying the modified call control commands to the ear piece. In anembodiment, the peripheral device may receive call control commands fromthe ear piece and may validate the call control commands generated bythe peripheral device and/or received from the ear piece prior tosending the call control commands generated by the peripheral deviceand/or received from the ear piece to the mobile phone. In anembodiment, validating call control commands may include comparinggenerated and/or received call control commands to previously sent callcontrol commands to ensure duplicate or conflicting call controlcommands are not sent to the mobile phone.

FIG. 1 illustrates a multiple subscriber device system 100 suitable foruse with the various embodiments. The multiple subscriber device system100 may include multiple devices, such as a mobile phone 102, a wirelessearpiece 104, and a peripheral device 106, such as a personal hub. Themobile phone 102 may exchange information, such as call control commandsand audio data, with a cellular network 114 over a cellular connection116, including CDMA, TDMA, GSM, PCS, 3G, 4G, LTE, or any other typeconnection, to establish voice calls over the cellular network 114. Themobile phone 102 and ear piece 104 may exchange data via one or moreradio links 108. As an example, the one or more radio links 108 betweenthe mobile phone 102 and the ear piece 104 may be one or more Bluetooth®connections, one or more Peanut connections, one or more Wi-Ficonnections, one or more ANT+ connections, and/or one or more of anyother type radio connections. The mobile phone 102 and the peripheraldevice 106 may exchange data via one or more radio links 110. As anexample, the one or more radio links 110 between the mobile phone 102and the peripheral device 106 may be one or more Bluetooth® connections,one or more Peanut connections, one or more Wi-Fi connections, one ormore ANT+ connections, and/or one or more of any other type radioconnections. The ear piece 104 and the peripheral device 106 mayexchange data via one or more radio links 112. As an example, the one ormore radio links 112 between the ear piece 104 and the peripheral device106 may be one or more Bluetooth® connections, one or more Peanutconnections, one or more Wi-Fi connections, one or more ANT+connections, and/or one or more of any other type radio connections.

FIG. 2 is a communication flow diagram illustrating example radio linkexchanges in a multiple subscriber device system 200 including a mobilephone 202, ear piece 204, and peripheral device 216. In an embodiment,the mobile phone 202 and ear piece 204 may establish a first radio link206 for exchanging call control commands, such as AT command packets208, 212, and audio data, such as audio data packets 210, 214. In anembodiment, the first radio link 206 may be a standard Bluetooth® linkas defined by the Bluetooth® Hands-Free Profile, including both a callcontrol (i.e., service) connection for exchanging call control commands,such as AT command packets 208, 212, and an audio connection forexchanging audio data, such as audio data packets 210, 214. In anembodiment, the AT command packets 208, 212 and the audio data packets210, 214 may be multiplexed together over the first radio link 206. ATcommand packets 208, 212 and audio data packets 210, 214 may be sentfrom the mobile phone 202 to the ear piece 204 and/or sent from the earpiece 204 to the mobile phone 202.

In an embodiment, a first out of band link 218 may be establishedbetween the ear piece 204 and the peripheral device 216. As an example,the first out of band link 218 may be a radio link not establishedaccording to the Bluetooth® Hands-Free Profile, such as a separateBluetooth® link, Peanut, Wi-Fi, ANT+, or other radio link notestablished according to the Bluetooth® Hands-Free Profile. In anembodiment, the ear piece 204 may receive the AT command packets 208,212 and audio data packets 210, 214 from the mobile phone 202 and mayseparate the AT command packets 208, 212 from the audio data packets210, 214. As an example, the ear piece 204 may separate call controlcommands from audio data by de-multiplex the AT command packets 208, 212from the audio data packets 210, 214. In an embodiment, the ear piece204 may consume the audio data packets 210, 214, for example, byutilizing the audio data packets 210, 214 to output audio on a speakerof the ear piece 204. The ear piece 204 may send the AT command packets208, 212 received from the mobile phone 202 to the peripheral device 216via the first out of band link 218. The peripheral device 216 mayreceive the AT command packets 208, 212 and may consume the AT commandpackets 208, 212, for example, by utilizing the AT command packets 208,212 to indicate on a display of the peripheral device 316 that a voicecall has been established.

In an embodiment, the peripheral device 216 may generate call controlcommands, such as AT command packets 208, 212. As an example callcontrol commands generated by the peripheral device 216 may include ahang-up command corresponding to a user selection of an end call icon ona touch screen of the peripheral device 216. In an embodiment, theperipheral device 216 may send the peripheral device 216 originated callcontrol commands, such as AT command packets 208, 212, to the ear piece204 via the first out of band link 218. The ear piece 204 may receivethe peripheral device 216 originated AT command packets 208, 212 and maysend the peripheral device 216 originated AT command packets 208, 212 tothe mobile phone 202 via the first radio link 206. As an example, theear piece 204 may send the peripheral device 216 originated AT commandpackets 208, 212 to the mobile phone 202 via the first radio link 206 bymultiplexing the peripheral device 216 originated AT command packets208, 212 with ear piece originated audio data packets 210, 214 sent overthe standard Bluetooth® link as defined by the Bluetooth® Hands-FreeProfile. In an embodiment, a second out of band link 224 may beestablished between the mobile phone 202 and the peripheral device 216.As an example, the second out of band link 224 may be a radio link notestablished according to the Bluetooth® Hands-Free Profile, such as aseparate Bluetooth® link, Peanut, Wi-Fi, ANT+, or other radio link notestablished according to the Bluetooth® Hands-Free Profile. As aspecific example, the second out of band link 224 may be a Bluetooth®link established according to the Bluetooth® Phone Book Access Profile.In an embodiment, the second out of band link 224 may be used by theperipheral device to request and/or receive phonebook information fromthe mobile phone, such as phone numbers, contact information, callhistory information, etc.

FIG. 3 is a communication flow diagram illustrating example radio linkexchanges in a multiple subscriber device system 300 including a mobilephone 302, ear piece 304, and peripheral device 316. In an embodiment,the mobile phone 302 and ear piece 304 may establish a first radio link306 for exchanging call control commands, such as AT command packets308, 312, and audio data, such as audio data packets 310, 314. In anembodiment, the first radio link 306 may be a standard Bluetooth® linkas defined by the Bluetooth® Hands-Free Profile, including both a callcontrol (i.e., service) connection for exchanging call control commands,such as AT command packets 308, 312, and an audio connection forexchanging audio data, such as audio data packets 310, 314. In anembodiment, the AT command packets 308, 312 and the audio data packets310, 314 may be multiplexed together over the first radio link 306. ATcommand packets 308, 312 and audio data packets 310, 314 may be sentfrom the mobile phone 302 to the ear piece 304 and/or sent from the earpiece 304 to the mobile phone 302.

In an embodiment, a first out of band link 318 may be establishedbetween the ear piece 304 and the mobile phone 302. As an example, thefirst out of band link 318 may be a radio link not established accordingto the Bluetooth® Hands-Free Profile, such as a separate Bluetooth®link, Peanut, Wi-Fi, ANT+, or other radio link not established accordingto the Bluetooth® Hands-Free Profile. In an embodiment, the ear piece304 may receive the AT command packets 308, 312 and audio data packets310, 314 from the mobile phone 302 and may separate the AT commandpackets 308, 312 from the audio data packets 310, 314. As an example,the ear piece 304 may separate call control commands from audio data byde-multiplex the AT command packets 308, 312 from the audio data packets310, 314. In an embodiment, the ear piece 304 may consume the audio datapackets 310, 314, for example, by utilizing the audio data packets 310,314 to output audio on a speaker of the ear piece 304. The ear piece 304may send the AT command packets 308, 312 received from the mobile phone302 to the mobile phone 302 via the first out of band link 318. Themobile phone 302 may receive the AT command packets 308, 312 and mayprovide the AT command packets 308, 312 to a hub application resident onthe mobile phone 302.

In an embodiment, a second out of band link 320 may be establishedbetween the mobile phone 302 and peripheral device 316. As an example,the second out of band link 320 may be a radio link not establishedaccording to the Bluetooth® Hands-Free Profile, such as a separateBluetooth® link, Peanut, Wi-Fi, ANT+, or other radio link notestablished according to the Bluetooth® Hands-Free Profile. In anembodiment, the establishment of the second out of band link 320 may beinitiated by the hub application resident on the mobile phone 302. In anembodiment, the hub application resident on the mobile phone 302 mayreceive the AT command packets 308, 312 originated on the mobile phone302 via the first out of band link 318 and may send the AT commandpackets 308, 312 to the peripheral device 316 via the second out of bandlink 320. The peripheral device 316 may receive the AT command packets308, 312 and may consume the AT command packets 308, 312, for example,by utilizing the AT command packets 308, 312 to indicate on a display ofthe peripheral device 316 that a voice call has been established. In afurther embodiment, phonebook information 322 may also be sent from themobile phone 302 to the peripheral device 316 over the second out ofband link 320.

In an embodiment, the peripheral device 316 may generate call controlcommands, such as AT command packets 308, 312. As an example callcontrol commands generated by the peripheral device 316 may include ahang-up command corresponding to a user selection of an end call icon ona touch screen of the peripheral device 316. In an embodiment, theperipheral device 316 may send the peripheral device 316 originated callcontrol commands, such as AT command packets 308, 312, to the hubapplication resident on the mobile phone 302. The hub applicationresident on the mobile phone 302 may receive the peripheral device 316originated call control commands, such as AT command packets 308, 312,and may send the call control commands to the ear piece 304 via thefirst out of band link 318. The ear piece 304 may receive the peripheraldevice 316 originated AT command packets 308, 312 and may send theperipheral device 316 originated AT command packets 308, 312 to themobile phone 302 via the first radio link 206. As an example, the earpiece 304 may send the peripheral device 316 originated AT commandpackets 308, 312 to the mobile phone 302 via the first radio link 306 bymultiplexing the peripheral device 316 originated AT command packets308, 312 with ear piece originated audio data packets 310, 314 sent overthe standard Bluetooth® link as defined by the Bluetooth® Hands-FreeProfile.

FIG. 4 is a communication flow diagram illustrating example radio linkexchanges in a multiple subscriber device system 400 including a mobilephone 402, ear piece 404, and peripheral device 416. In an embodiment,the mobile phone 402 and peripheral device 416 may establish a firstradio link 406 for exchanging call control commands, such as AT commandpackets 408, 412, and audio data, such as audio data packets 410, 414.In an embodiment, the first radio link 406 may be a standard Bluetooth®link as defined by the Bluetooth® Hands-Free Profile, including both acall control (i.e., service) connection for exchanging call controlcommands, such as AT command packets 408, 412, and an audio connectionfor exchanging audio data, such as audio data packets 410, 414. In anembodiment, the AT command packets 408, 412 and the audio data packets410, 414 may be multiplexed together over the first radio link 406. ATcommand packets 408, 412 and audio data packets 410, 414 may be sentfrom the mobile phone 402 to the peripheral device 416 and/or sent fromthe peripheral device 416 to the mobile phone 402.

In an embodiment, the peripheral device 416 and ear piece 404 mayestablish a second radio link 418 for exchanging call control commands,such as AT command packet 412, and audio data, such as audio datapackets 410, 414. In an embodiment, the second radio link 418 may be astandard Bluetooth® link as defined by the Bluetooth® Hands-FreeProfile, including both a call control (i.e., service) connection forexchanging call control commands, such as AT command packet 412, and anaudio connection for exchanging audio data, such as audio data packets410, 414. In an embodiment, the AT command packets 412 and the audiodata packets 410, 414 may be multiplexed together over the second radiolink 418. AT command packet 412 and audio data packets 410, 414 may besent from the peripheral device 416 to the ear piece 404 and/or sentfrom the ear piece 404 to the peripheral device 416.

In an embodiment, the peripheral device 416 may receive the AT commandpackets 408, 412 and audio data packets 410, 414 from the mobile phone402 and may separate the AT command packets 408, 412 from the audio datapackets 410, 414. As an example, the peripheral device 416 may separatecall control commands from audio data by de-multiplex the AT commandpackets 408, 412 from the audio data packets 410, 414. In an embodiment,the peripheral device 416 may consume all or a portion of the AT commandpackets 408, 412, for example, for example, by utilizing the AT commandpackets 408, 412 to indicate on a display of the peripheral device 416that a voice call has been established. In a further embodiment, theperipheral device 416 may modify one or more of the mobile phoneoriginated call control commands, for example by changing an AT commandpacket 412, and may combine the modified call control command with themobile phone originated audio data, for example by multiplexing themodified AT command packet 412 with the audio data packets 410, 414. Theperipheral device 416 may send the modified AT command packet 412 andthe audio data packets 410, 414 to the ear piece via the second radiolink 418. The ear piece 404 may receive the AT command packet 412, andaudio data packets 410, 414 and may consume the modified AT commandpacket 412, for example, by utilizing the modified AT command packet 412to generate an audible ring indication from a speaker of the ear piece404. The ear piece 404 may consume the audio data packets 410, 414 byutilizing the audio data packets 410, 414 to output audio on a speakerof the ear piece 404.

In an embodiment, the ear piece 404 may generate call control commands,such as AT command packet 412. As an example a call control commandgenerated by the ear piece 404 may include a hang-up commandcorresponding to a button press event on the ear piece 404.Additionally, the ear piece 404 may generate audio data, such as audiodata packets 410, 414. In an embodiment, the ear piece 404 may send theear piece 404 originated call control commands, such as AT commandpacket 412, and the ear piece 404 originated audio data, such as audiodata packets 410, 414 to the peripheral device 416 via the second radiolink 416. As an example, the ear piece 404 may send the ear pieceoriginated AT command packet 412 and audio data packets 410, 414 to theperipheral device 416 via the second radio link 418 by multiplexing theear piece 404 originated AT command packet 412 with ear piece originatedaudio data packets 410, 414 sent over the standard Bluetooth® link asdefined by the Bluetooth® Hands-Free Profile. The peripheral device 416may receive the ear piece 404 originated AT command packet 412 and audiodata packets 410, 414. In an embodiment, the peripheral device 416 mayvalidate the AT command packet 412 received from the ear piece 404 toensure call control command is not a duplicate of a call control commandalready sent by the peripheral device 416 to the mobile phone 402. As anexample, a user may erroneously press a button on an ear piece 404indicating to answer a call even though the user already indicated toanswer a call via the touch screen display of the peripheral device 416.The validation preventing the second call control command received fromthe ear piece 404 from being forwarded to the mobile phone 402, mayprevent duplicate or conflicting call control commands from beingreceived at the mobile phone 402. The peripheral device 416 may generatecall control commands, and valid call control commands originated by theperipheral device 416 and or the ear piece 404, such as AT commandpackets 408, 412, may be sent along with audio data originated by theear piece 404, such as audio data packets 410, 414 to the mobile phone402 via the first radio link 406. As an example, the peripheral device416 may send the valid call control commands originated by theperipheral device 416 and or the ear piece 404, such as AT commandpackets 408, 412 and audio data originated by the ear piece 404, such asaudio data packets 410, 414 to the mobile phone 402 via the first radiolink 406 by multiplexing the valid AT command packets 408, 412 with earpiece originated audio data packets 410, 414 sent over the standardBluetooth® link as defined by the Bluetooth® Hands-Free Profile.

FIG. 5 illustrates an embodiment method 500 for providing call controlinformation from a mobile phone to another device. In an embodiment, theoperations of method 500 may be performed by the processors of devicesin a multiple subscriber device system, such as a multiple subscriberdevice system including a mobile phone, ear piece, and peripheraldevice, such as a personal hub. In blocks 502 and 504 the mobile phoneand ear piece may perform operations to establish a standard Bluetooth®link as defined by the Bluetooth® Hands-Free Protocol (“BT HFP”),including both a service level connection for exchanging call controlcommands and an audio connection for exchanging audio data. In block 506the mobile phone may send call control command and audio data via the BTHFP link to the ear piece, and in block 508 the ear piece may receivethe call control command and audio data via the BT HFP link. In anembodiment, the call control commands and the audio data may be sent viathe BT HFP link as multiplexed packets. In block 510 the ear piece mayseparate the call control commands from the audio data. In anembodiment, the ear piece may separate the call control commands fromthe audio data by de-multiplexing the call control commands from theaudio data.

At blocks 512 and 514 the ear piece and peripheral device may performoperations to establish an out of band link. In an embodiment, the outof band link established between the ear piece and the peripheral devicemay be a radio link not established according to the Bluetooth®Hands-Free Profile, such as a separate Bluetooth® link, Peanut, Wi-Fi,ANT+, or other radio link not established according to the Bluetooth®Hands-Free Profile. In block 516 the ear piece may send the call controlcommand received from the mobile phone to the peripheral device via theout of band link, and in block 518 the peripheral device may receive thecall control command via the out of band link. In block 520 theperipheral device may consume the call control command. As an example,the peripheral device may consume the call control command by utilizingthe call control command packets to indicate on a display of theperipheral device that a voice call has been established.

At block 522 the peripheral device may generate a call control command.As an example, a call control command may be a hang up command generatedin response to an indication of a user selection of a terminate calloption at the peripheral device. In block 524 the peripheral device maysend the call control command originated at the peripheral device to theear piece via the out of band link, and in block 526 the ear phone mayreceive the peripheral device originated call control command via theout of band link. In block 528 the ear piece may send the peripheraldevice originated call control command to the mobile phone via the BTHFP link, and in block 530 the mobile phone may receive the peripheraldevice originated call control command via the BT HFP link.

At blocks 532 and 534 the mobile phone and peripheral device may performoperations to establish an out of band link between the mobile phone andthe peripheral device. In an embodiment, the out of band linkestablished between the mobile phone and the peripheral device may be aradio link not established according to the Bluetooth® Hands-FreeProfile, such as a separate Bluetooth® link, Peanut, Wi-Fi, ANT+, orother radio link not established according to the Bluetooth® Hands-FreeProfile. As an example, the out of band link established between themobile phone and the peripheral device may be a Bluetooth® linkestablished according to the Bluetooth® Phone Book Access Profile. In anembodiment, the out of band link may be established between the mobilephone and peripheral device at anytime, such as before the BT HFP linkis established between the mobile phone and ear piece, simultaneouslywith the establishment of the BT HFP, or after the establishment of theBT HFP. In block 536 the peripheral device may send a phone bookinformation request to the mobile phone over the out of band link, andin block 538 the mobile phone may receive the phone book informationrequest over the out of band link. In block 540 the mobile phone maysend phone book information over the out of band link, and in block 542the peripheral device may receive the phone book information over theout of band link from the mobile phone. As examples, phone bookinformation may include phone numbers, contact information, call historyinformation, etc. In the various embodiments, phone book information maybe used by the device receiving the phone book information in anymanner, such as to match incoming phone numbers with contact informationand/or to match selected contacts with phone numbers for dialingoutgoing calls.

FIG. 6 illustrates an embodiment method 600 for providing call controlinformation from a mobile phone to another device similar to method 500described above with reference to FIG. 5, except that in method 600 anout of band link between the ear piece and peripheral device may not beestablished. Rather, in method 600 call control information is routedfrom the ear piece, back through the mobile phone, and then to theperipheral device. In blocks 502, 504, 506, 508, and 510 the mobilephone and ear piece perform operations of like numbered blocks of method500 described above with reference to FIG. 5 to establish a BT HFP link,send and receive call control commands and audio data via the BT HFPlink, and separate the call control commands from the audio data.

At blocks 602 and 604 the ear piece and mobile device may performoperations to establish an out of band link between the ear piece andthe mobile device. In an embodiment, the out of band link establishedbetween the ear piece and the mobile phone may be a radio link notestablished according to the Bluetooth® Hands-Free Profile, such as aseparate Bluetooth® link, Peanut, Wi-Fi, ANT+, or other radio link notestablished according to the Bluetooth® Hands-Free Profile. In block 606the ear piece may send the mobile phone originated call control commandto the mobile phone via the out of band link between the ear piece andmobile phone. In block 608 the mobile phone may receive the mobile phoneoriginated call control command via the out of band link between the earpiece and mobile phone. In an embodiment, the call control command maybe received in a hub application running on a processor of the mobiledevice.

At blocks 610 and 612 the mobile phone and peripheral device may performoperations to establish an out of band link between the mobile phone andthe peripheral device. In an embodiment, the out of band linkestablished between the mobile phone and the peripheral device may be aradio link not established according to the Bluetooth® Hands-FreeProfile, such as a separate Bluetooth® link, Peanut, Wi-Fi, ANT+, orother radio link not established according to the Bluetooth® Hands-FreeProfile. In block 614 the mobile phone may send the call control commandto the peripheral device via the out of band link between the mobilephone and the peripheral device. In an embodiment, phone bookinformation may also be sent to the peripheral device via the out ofband link between the mobile phone and the peripheral device. In block616 the peripheral device may receive the call control command and phonebook information from the mobile phone via the out of band link. Inblock 618 the peripheral device may consume the call control command. Asan example, the peripheral device may consume the call control commandby utilizing the call control command packets to indicate on a displayof the peripheral device that a voice call has been established.

At block 620 the peripheral device may generate a call control command.As an example, a call control command may be a hang up command generatedin response to an indication of a user selection of a terminate calloption at the peripheral device. In block 622 the peripheral device maysend the call control command originated at the peripheral device to themobile device via the out of band link between the peripheral device andthe mobile device. In block 624 the mobile device may receive theperipheral device originated call control command from the peripheraldevice via the out of band link. In an embodiment, the peripheral deviceoriginated call control command may be received at a hub applicationrunning on a processor of the mobile device. In block 626 the mobiledevice may send the peripheral device originated call controlinformation to the ear piece via the out of band link between the mobiledevice and ear piece. In block 628 the ear piece may receive theperipheral device originated call control command from the mobile devicevia the out of band link between the mobile device and ear piece. Inblock 630 the ear piece may send the peripheral device originated callcontrol command to the mobile phone via the BT HFP link, and in block632 the mobile phone may receive the peripheral device originated callcontrol command via the BT HFP link.

FIG. 7 illustrates an embodiment method 700 for providing call controlinformation from a mobile phone to another device. In an embodiment, theoperations of method 700 may be performed by the processors of devicesin a multiple subscriber device system, such as a multiple subscriberdevice system including a mobile phone, ear piece, and peripheraldevice, such as a personal hub. In blocks 702 and 704 the mobile phoneand peripheral device may perform operations to establish a standardBluetooth® link as defined by the Bluetooth® Hands-Free Protocol (“BTHFP”), including both a service level connection for exchanging callcontrol commands and an audio connection for exchanging audio data. Inblock 706 the mobile phone may send call control command and audio datavia the BT HFP link to the peripheral device, and in block 708 theperipheral device may receive the call control command and audio datavia the BT HFP link. In an embodiment, the call control commands and theaudio data may be sent via the BT HFP link as multiplexed packets. Inblock 710 the peripheral device may separate the call control commandsfrom the audio data. In an embodiment, the peripheral device mayseparate the call control commands from the audio data byde-multiplexing the call control commands from the audio data. In block712 the peripheral device may consume the call control command. As anexample, the peripheral device may consume the call control command byutilizing the call control command packets to indicate on a display ofthe peripheral device that a voice call has been established. In block714 the peripheral device may modify a call control command and combinethe modified call control command with the mobile phone originated audiodata. As an example, the peripheral device may combine the modified callcontrol command and the mobile phone originated audio data bymultiplexing the modified call control command and mobile phoneoriginated audio data.

At blocks 716 and 718 the peripheral device and ear piece may performoperations to establish a standard Bluetooth® link as defined by theBluetooth® Hands-Free Protocol (“BT HFP”), including both a servicelevel connection for exchanging call control commands and an audioconnection for exchanging audio data. In block 720 the peripheral devicemay send audio data and any modified call control command via the BT HFPlink to the ear piece, and in block 722 the peripheral device mayreceive the audio data and any modified call control command via the BTHFP link. In an embodiment, the modified call control commands and theaudio data may be sent via the BT HFP link as multiplexed packets. Inblock 726 the ear piece may consume the audio data and any modified callcontrol command. As an example, the ear piece may consume the audio databy outputting sound from a speaker using the audio data and may consumethe modified call control command by outputting a ring indication from aspeaker of the ear piece.

At block 724 the peripheral device may generate a call control command.As an example, a call control command may be a hang up command generatedin response to an indication of a user selection of a terminate calloption at the peripheral device. In parallel, in block 728 the ear piecemay generate audio data, such as voice data received from a microphoneof the ear piece. In an optional embodiment, at optional block 730 theear piece may also generate a call control command. As an example, acall control command may be a hang up command generated in response to abutton press indication at the ear piece. In block 732 the ear piece maysend the ear piece originated audio data and any call control command tothe peripheral device via the BT HFP link between the ear piece and theperipheral device. In block 734 the peripheral device may receive theaudio data and any call control command received from the ear piece viathe BT HFP link between the peripheral device and ear piece. In block736 the peripheral device may validate the call control commands. In anembodiment, validating call control commands may include comparing callcommands generated by the peripheral device and received call controlcommands originated by the ear piece to call control commands previouslysent by the peripheral device to the mobile phone. As an example, theperipheral device may log the type of call control commands sent to themobile device, and may prevent duplicate or conflicting call controlcommands from being sent to the mobile phone. In block 738 theperipheral device may send the ear piece originated audio data and anyvalid call control commands to the mobile phone via the BT HFP link, andin block 740 the mobile phone may receive the ear piece originated audiodata and any valid call control commands via the BT HFP link.

The various embodiments described above may be implemented within avariety of peripheral devices, such as personal hubs. FIG. 8 illustratesan example peripheral device, a wrist watch type personal hub 800. Apersonal hub 800 may include a processor 802 coupled to internalmemories 804 and 806. Internal memories 804 and 806 may be volatile ornon-volatile memories, and may also be secure and/or encrypted memories,or unsecure and/or unencrypted memories, or any combination thereof. Theprocessor 802 may also be coupled to a touch screen display 820, such asa resistive-sensing touch screen, capacitive-sensing touch screeninfrared sensing touch screen, or the like. Additionally, the personalhub 800 may have one or more antenna 808 for sending and receivingelectromagnetic radiation that may be connected to one or more wirelessdata links 812, such as one or more Bluetooth® transceivers, Peanuttransceivers, Wi-Fi transceivers, ANT+ transceivers, etc., which may becoupled to the processor 802. The personal hub 800 may also includephysical buttons 822 and 810 for receiving user inputs as well as aslide sensor 816 for receiving user inputs.

The various embodiments may be implemented in any of a variety of mobiletelephones, an example of which is illustrated in FIG. 9. For example,the mobile device 900 may include a processor 902 coupled to internalmemories 904 and 910. Internal memories 904 and 910 may be volatile ornon-volatile memories, and may also be secure and/or encrypted memories,or unsecure and/or unencrypted memories, or any combination thereof. Theprocessor 902 may also be coupled to a touch screen display 906, such asa resistive-sensing touch screen, capacitive-sensing touch screeninfrared sensing touch screen, or the like. Additionally, the display ofthe mobile device 900 need not have touch screen capability.Additionally, the mobile device 900 may have one or more antenna 908 forsending and receiving electromagnetic radiation that may be connected toone or more wireless data links and/or cellular telephone transceivers916, such as one or more Bluetooth® transceivers, Peanut transceivers,Wi-Fi transceivers, ANT+ transceivers, cellular (e.g., CDMA, TDMA, GSM,PCS, 3G, 4G, LTE, etc.) transceivers, etc., which may be coupled to theprocessor 902. The mobile device 900 may also include physical buttons912 a and 912 b for receiving user inputs. The mobile device 900 mayalso include a power button 918 for turning the mobile device 900 on andoff.

The various embodiments described above may also be implemented within avariety of wireless earpieces, such as wireless earpiece 1000illustrated in FIG. 10A. A wireless earpiece 1000 may include aprocessor 1002 coupled to internal memories 1004 and 1006. Internalmemories 1004 and 1006 may be volatile or non-volatile memories, and mayalso be secure and/or encrypted memories, or unsecure and/or unencryptedmemories, or any combination thereof. The wireless earpiece 1000 mayinclude a physical button 1014 for receiving user inputs. Additionally,the wireless earpiece 1000 may have one or more antenna 1012 for sendingand receiving electromagnetic radiation that may be connected to awireless data link 1013 such as one or more Bluetooth® transceivers,Peanut transceivers, Wi-Fi transceivers, ANT+ transceivers, etc., whichmay be coupled to the processor 1002. The wireless earpiece 1000 mayinclude a speaker 1008 coupled to the processor 1002 and configured togenerate an audio output. The wireless earpiece 1000 may also include amicrophone 1016 coupled to the processor 1002 to receive an audio input.

FIG. 10B illustrates an alternative embodiment of the wireless earpiece1000 in which the microphone 1016 may be positioned within a mainhousing of the wireless earpiece 1000 rather than on a microphone boomextending toward the user's mouth when the wireless earpiece is worn. Inan embodiment, the microphone 1016 may be a directional microphone, andthe earpiece housing may be configured such that the microphone 1016 ispointed toward the mouth of the user when the user may be wearing theearpiece 1016. Further audio processing of microphone data may be usedto further direct the microphone sensitivity in order to capture audiodata from the user's mouth. In this manner, the microphone 1016 mayreceive audio input from the user of the wireless earpiece 1016.

The processors 802, 902, and 1002 may be any programmablemicroprocessor, microcomputer or multiple processor chip or chips thatcan be configured by software instructions (applications) to perform avariety of functions, including the functions of the various embodimentsdescribed above. In some devices, multiple processors may be provided,such as one processor dedicated to wireless communication functions andone processor dedicated to running other applications. Typically,software applications may be stored in the internal memory 804, 806,904, 910, 1004, and 1006 before they are accessed and loaded into theprocessors 802, 902, and 1002. The processors 802, 802, and 1002 mayinclude internal memory sufficient to store the application softwareinstructions. In many devices the internal memory may be a volatile ornonvolatile memory, such as flash memory, or a mixture of both. For thepurposes of this description, a general reference to memory refers tomemory accessible by the processors 802, 902, and 1002 includinginternal memory or removable memory plugged into the device and memorywithin the processor 802, 902, and 1002 themselves.

The foregoing method descriptions and the process flow diagrams areprovided merely as illustrative examples and are not intended to requireor imply that the steps of the various embodiments must be performed inthe order presented. As will be appreciated by one of skill in the artthe order of steps in the foregoing embodiments may be performed in anyorder. Words such as “thereafter,” “then,” “next,” etc. are not intendedto limit the order of the steps; these words are simply used to guidethe reader through the description of the methods. Further, anyreference to claim elements in the singular, for example, using thearticles “a,” “an” or “the” is not to be construed as limiting theelement to the singular.

The various illustrative logical blocks, modules, circuits, andalgorithm steps described in connection with the embodiments disclosedherein may be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,circuits, and steps have been described above generally in terms oftheir functionality. Whether such functionality is implemented ashardware or software depends upon the particular application and designconstraints imposed on the overall system. Skilled artisans mayimplement the described functionality in varying ways for eachparticular application, but such implementation decisions should not beinterpreted as causing a departure from the scope of the presentinvention.

The hardware used to implement the various illustrative logics, logicalblocks, modules, and circuits described in connection with the aspectsdisclosed herein may be implemented or performed with a general purposeprocessor, a digital signal processor (DSP), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA) orother programmable logic device, discrete gate or transistor logic,discrete hardware components, or any combination thereof designed toperform the functions described herein. A general-purpose processor maybe a microprocessor, but, in the alternative, the processor may be anyconventional processor, controller, microcontroller, or state machine. Aprocessor may also be implemented as a combination of computing devices,e.g., a combination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration. Alternatively, some steps ormethods may be performed by circuitry that is specific to a givenfunction.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored as one or moreinstructions or code on a non-transitory computer-readable medium ornon-transitory processor-readable medium. The steps of a method oralgorithm disclosed herein may be embodied in a processor-executablesoftware module which may reside on a non-transitory computer-readableor processor-readable storage medium. Non-transitory computer-readableor processor-readable storage media may be any storage media that may beaccessed by a computer or a processor. By way of example but notlimitation, such non-transitory computer-readable or processor-readablemedia may include RAM, ROM, EEPROM, FLASH memory, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium that may be used to store desired programcode in the form of instructions or data structures and that may beaccessed by a computer. Disk and disc, as used herein, includes compactdisc (CD), laser disc, optical disc, digital versatile disc (DVD),floppy disk, and blu-ray disc where disks usually reproduce datamagnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofnon-transitory computer-readable and processor-readable media.Additionally, the operations of a method or algorithm may reside as oneor any combination or set of codes and/or instructions on anon-transitory processor-readable medium and/or computer-readablemedium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the presentinvention. Various modifications to these embodiments will be readilyapparent to those skilled in the art, and the generic principles definedherein may be applied to other embodiments without departing from thespirit or scope of the invention. Thus, the present invention is notintended to be limited to the embodiments shown herein but is to beaccorded the widest scope consistent with the following claims and theprinciples and novel features disclosed herein.

What is claimed is:
 1. A method of managing a call on a communicationdevice, comprising: receiving a mobile phone originated call controlcommand and audio data from a mobile phone at the communication devicevia a first radio link; and separating the mobile phone originated callcontrol command from the audio data at the communication device.
 2. Themethod of claim 1, further comprising establishing the first radio linkbetween the mobile phone and the communication device, wherein the firstradio link is a first Bluetooth® link including a call controlconnection and a first audio connection.
 3. The method of claim 2,wherein the communication device is an ear piece, the method furthercomprising: establishing a first out of band link between the ear pieceand a peripheral device; and sending the received mobile phoneoriginated call control command from the ear piece to the peripheraldevice via the first out of band link.
 4. The method of claim 3, furthercomprising: receiving a peripheral device originated call controlcommand at the ear piece via the first out of band link; and sending theperipheral device originated call control command from the ear piece tothe mobile phone via the first Bluetooth® link.
 5. The method of claim4, wherein the first out of band link is a second Bluetooth® link. 6.The method of claim 4, further comprising: establishing a second out ofband link between the mobile phone and the peripheral device; andsending phonebook information from the mobile phone to the peripheraldevice over the second out of band link.
 7. The method of claim 2,wherein the communication device is an ear piece, the method furthercomprising: establishing a first out of band link between the ear pieceand the mobile phone; establishing a second out of band link between themobile phone and a peripheral device; sending the received mobile phoneoriginated call control command from the ear piece to the mobile phonevia the first out of band link; receiving the mobile phone originatedcall control command sent from the ear piece in a hub applicationresident on the mobile phone; sending the mobile phone originated callcontrol command from the hub application to the peripheral device viathe second out of band link; and receiving the mobile phone originatedcall control command sent from the hub application at the peripheraldevice.
 8. The method of claim 7, further comprising: receiving aperipheral device originated call control command in the hub applicationresident on the mobile phone via the second out of band link; sendingthe peripheral device originated call control command from the hubapplication to the ear piece via the first out of band link; receivingthe peripheral device originated call control command at the ear piecevia the first out of band link; and sending the peripheral deviceoriginated call control command from the ear piece to the mobile phonevia the first Bluetooth® link.
 9. The method of claim 7, wherein theperipheral device is a wireless personal hub, the first out of band linkis a second Bluetooth® link, and the second out of band link is a thirdBluetooth® link.
 10. The method of claim 7, further comprising: sendingphonebook information from the mobile phone to the peripheral deviceover the second out of band link.
 11. The method of claim 2, wherein thecommunication device is a peripheral device, the method furthercomprising: establishing a second Bluetooth® link between the peripheraldevice and an ear piece, the second Bluetooth® link including a callcontrol connection and a second audio connection between the ear pieceand the peripheral device; and sending the mobile phone originated audiodata from the peripheral device to the ear piece via the secondBluetooth® link.
 12. The method of claim 11, further comprising:receiving ear piece originated call control command and audio data fromthe ear piece at the peripheral device via the second Bluetooth® link;sending the ear piece originated call control command and audio datafrom the peripheral device to the mobile phone over the first audioconnection over the first Bluetooth® link; and receiving the ear pieceoriginated call control command and audio data at the mobile phone viathe first Bluetooth® link.
 13. The method of claim 11, furthercomprising: modifying the mobile phone originated call control commandat the peripheral device to generate a modified call control command;and combining the modified call control command and the mobile phoneoriginated audio data at the peripheral device, wherein sending themobile phone originated audio data from the peripheral device to the earpiece via the second Bluetooth® link comprises sending the modified callcontrol command and the mobile phone originated audio data to the earpiece via the second Bluetooth® link.
 14. A communication device,comprising: a transceiver; a memory; and a processor connected to thetransceiver and the memory, wherein the processor is configured withprocessor-executable instructions to perform operations comprising:receiving a mobile phone originated call control command and audio datafrom a mobile phone via a first radio link; and separating the mobilephone originated call control command from the audio data.
 15. Thecommunication device of claim 14, further comprising establishing thefirst radio link with a mobile phone, wherein the first radio link is afirst Bluetooth® link including a call control connection and a firstaudio connection.
 16. The communication device of claim 15, wherein thecommunication device is an ear piece, and wherein the processor isconfigured with processor-executable instructions to perform operationsfurther comprising: establishing a first out of band link with aperipheral device; and sending the received mobile phone originated callcontrol command to the peripheral device via the first out of band link.17. The communication device of claim 16, wherein the processor isconfigured with processor-executable instructions to perform operationsfurther comprising: receiving a peripheral device originated callcontrol command via the first out of band link; and sending theperipheral device originated call control command to the mobile phonevia the first Bluetooth® link.
 18. The communication device of claim 17,wherein the first out of band link is a second Bluetooth® link.
 19. Thecommunication device of claim 15, wherein the communication device is aperipheral device, and wherein the processor is configured withprocessor-executable instructions to perform operations furthercomprising: establishing a second Bluetooth® link with an ear piece, thesecond Bluetooth® link including a call control connection and a secondaudio connection between the ear piece and the peripheral device; andsending the mobile phone originated audio data to the ear piece via thesecond Bluetooth® link.
 20. The communication device of claim 19,wherein the processor is configured with processor-executableinstructions to perform operations further comprising: receiving earpiece originated call control command and audio data from the ear piecevia the second Bluetooth® link; and sending the ear piece originatedcall control command and audio data to the mobile phone over the firstaudio connection over the first Bluetooth® link.
 21. The communicationdevice of claim 19, wherein the processor is configured withprocessor-executable instructions to perform operations furthercomprising: modifying the mobile phone originated call control commandto generate a modified call control command; and combining the modifiedcall control command and the mobile phone originated audio data, andwherein the processor is configured with processor-executableinstructions to perform operations such that sending the mobile phoneoriginated audio data to the ear piece via the second Bluetooth® linkcomprises sending the modified call control command and the mobile phoneoriginated audio data to the ear piece via the second Bluetooth® link.22. A communication device, comprising: means for receiving a mobilephone originated call control command and audio data from a mobile phonevia a first radio link; and means for separating the mobile phoneoriginated call control command from the audio data.
 23. Thecommunication device of claim 22, further comprising means forestablishing the first radio link with a mobile phone, wherein the firstradio link is a first Bluetooth® link including a call controlconnection and a first audio connection.
 24. The communication device ofclaim 23, wherein the communication device is an ear piece, thecommunication device further comprising: means for establishing a firstout of band link with a peripheral device; and means for sending thereceived mobile phone originated call control command to the peripheraldevice via the first out of band link.
 25. The communication device ofclaim 24, further comprising: means for receiving a peripheral deviceoriginated call control command via the first out of band link; andmeans for sending the peripheral device originated call control commandto the mobile phone via the first Bluetooth® link.
 26. The communicationdevice of claim 25, wherein the first out of band link is a secondBluetooth® link.
 27. The communication device of claim 23, wherein thecommunication device is a peripheral device, the communication devicefurther comprising: means for establishing a second Bluetooth® link withan ear piece, the second Bluetooth® link including a call controlconnection and a second audio connection between the ear piece and theperipheral device; and means for sending the mobile phone originatedaudio data to the ear piece via the second Bluetooth® link.
 28. Thecommunication device of claim 27, further comprising: means forreceiving ear piece originated call control command and audio data fromthe ear piece via the second Bluetooth® link; and means for sending theear piece originated call control command and audio data to the mobilephone over the first audio connection over the first Bluetooth® link.29. The communication device of claim 27, further comprising: means formodifying the mobile phone originated call control command to generate amodified call control command; and means for combining the modified callcontrol command and the mobile phone originated audio data, and whereinmeans for sending the mobile phone originated audio data to the earpiece via the second Bluetooth® link comprises means for sending themodified call control command and the mobile phone originated audio datato the ear piece via the second Bluetooth® link.
 30. A non-transitoryprocessor-readable storage medium having stored thereonprocessor-executable instructions configured to cause a processor of acommunication device to perform operations comprising: receiving amobile phone originated call control command and audio data from amobile phone via a first radio link; and separating the mobile phoneoriginated call control command from the audio data.
 31. Thenon-transitory processor-readable storage medium of claim 30, wherein:the stored processor-executable instructions are configured to cause aprocessor of the communication device to perform operations furthercomprising establishing the first radio link with the mobile phone; andthe stored processor-executable instructions are configured to cause aprocessor of the communication device to perform operations such thatthe first radio link is a first Bluetooth® link including a call controlconnection and a first audio connection.
 32. The non-transitoryprocessor-readable storage medium of claim 31, wherein the communicationdevice is an ear piece, and wherein the stored processor-executableinstructions are configured to cause a processor of an ear piece toperform operations further comprising: establishing a first out of bandlink with a peripheral device; and sending the received mobile phoneoriginated call control command to the peripheral device via the firstout of band link.
 33. The non-transitory processor-readable storagemedium of claim 32, wherein the stored processor-executable instructionsare configured to cause a processor of an ear piece to performoperations further comprising: receiving a peripheral device originatedcall control command via the first out of band link; and sending theperipheral device originated call control command to the mobile phonevia the first Bluetooth® link.
 34. The non-transitory processor-readablestorage medium of claim 32, wherein the stored processor-executableinstructions are configured to cause a processor of an ear piece toperform operations such that the first out of band link is a secondBluetooth® link.
 35. The non-transitory processor-readable storagemedium of claim 31, wherein the communication device is a peripheraldevice, wherein the stored processor-executable instructions areconfigured to cause a processor of a peripheral device to performoperations further comprising: establishing a second Bluetooth® linkwith an ear piece, the second Bluetooth® link including a call controlconnection and a second audio connection between the ear piece and theperipheral device; and sending the mobile phone originated audio data tothe ear piece via the second Bluetooth® link.
 36. The non-transitoryprocessor-readable storage medium of claim 35, wherein the storedprocessor-executable instructions are configured to cause a processor ofa peripheral device to perform operations further comprising: receivingear piece originated call control command and audio data from the earpiece via the second Bluetooth® link; and sending the ear pieceoriginated call control command and audio data to the mobile phone overthe first audio connection over the first Bluetooth® link.
 37. Thenon-transitory processor-readable storage medium of claim 35, whereinthe stored processor-executable instructions are configured to cause aprocessor of a peripheral device to perform operations furthercomprising: modifying the mobile phone originated call control commandto generate a modified call control command; and combining the modifiedcall control command and the mobile phone originated audio data, andwherein the stored processor-executable instructions are configured tocause a processor of a peripheral device to perform operations such thatsending the mobile phone originated audio data to the ear piece via thesecond Bluetooth® link comprises sending the modified call controlcommand and the mobile phone originated audio data to the ear piece viathe second Bluetooth® link.
 38. A communication system, comprising: amobile phone, comprising: a first transceiver; a first memory; and afirst processor connected to the first transceiver and the first memory;and a communication device, comprising: a second transceiver; a secondmemory; and a second processor connected to the second transceiver andthe second memory, wherein the first processor is configured withprocessor-executable instructions to perform operations comprising:establishing a first radio link with the communication device; andsending a mobile phone originated call control command and audio data tothe communication device via the first radio link, and wherein thesecond processor is configured with processor-executable instructions toperform operations comprising: establishing the first radio link withthe mobile phone; receiving the mobile phone originated call controlcommand and audio data from the mobile phone via the first radio link;and separating the mobile phone originated call control command from theaudio data.
 39. The communication system of claim 38, wherein the firstradio link is a first Bluetooth® link including a call controlconnection and a first audio connection.
 40. The communication system ofclaim 39, wherein the communication device is an ear piece, thecommunication system further comprising: a peripheral device,comprising: a third transceiver; a third memory; and a third processorconnected to the third transceiver and the third memory, wherein thesecond processor is configured with processor-executable instructions toperform operations further comprising: establishing a first out of bandlink with the peripheral device; and sending the received mobile phoneoriginated call control command to the peripheral device via the firstout of band link, and wherein the third processor is configured withprocessor-executable instructions to perform operations comprising:establishing the first out of band link with the ear piece; andreceiving the mobile phone originated call control command from the earpiece via the first out of band link.
 41. The communication system ofclaim 40, wherein: the third processor is configured withprocessor-executable instructions to perform operations furthercomprising sending a peripheral device originated call control commandto the ear piece via the first out of band link; the second processor isconfigured with processor-executable instructions to perform operationsfurther comprising: receiving the peripheral device originated callcontrol command from the peripheral device via the first out of bandlink; and sending the peripheral device originated call control commandto the mobile phone via the first Bluetooth® link; and the firstprocessor is configured with processor-executable instructions toperform operations further comprising receiving the peripheral deviceoriginated call control command from the ear piece via the firstBluetooth® link.
 42. The communication system of claim 41, wherein thefirst out of band link is a second Bluetooth® link.
 43. Thecommunication system of claim 41, wherein: the first processor isconfigured with processor-executable instructions to perform operationsfurther comprising: establishing a second out of band link with theperipheral device; and sending phonebook information to the peripheraldevice over the second out of band link, and the third processor isconfigured with processor-executable instructions to perform operationsfurther comprising: establishing the second out of band link with themobile phone; and receiving phonebook information from the mobile phoneover the second out of band link.
 44. The communication system of claim39, wherein the communication device is an ear piece, the communicationsystem further comprising: a peripheral device, comprising: a thirdtransceiver; a third memory; and a third processor connected to thethird transceiver and the third memory, wherein the second processor isconfigured with processor-executable instructions to perform operationsfurther comprising: establishing a first out of band link with themobile phone; and sending the received mobile phone originated callcontrol command to the mobile phone via the first out of band link,wherein the first processor is configured with processor-executableinstructions to perform operations further comprising: establishing thefirst out of band link with the ear piece; receiving the mobile phoneoriginated call control command from the ear piece in a hub application;establishing a second out of band link with the peripheral device; andsending the mobile phone originated call control command from the hubapplication to the peripheral device via the second out of band link,and wherein the third processor is configured with processor-executableinstructions to perform operations comprising: establishing the secondout of band link with mobile phone; and receiving the mobile phoneoriginated call control command sent from the hub application.
 45. Thecommunication system of claim 44, wherein: the third processor isconfigured with processor-executable instructions to perform operationsfurther comprising: sending a peripheral device originated call controlcommand to the hub application via the second out of band link; thefirst processor is configured with processor-executable instructions toperform operations further comprising: receiving the peripheral deviceoriginated call control command in the hub application resident on themobile phone via the second out of band link; and sending the peripheraldevice originated call control command from the hub application to theear piece via the first out of band link; and the second processor isconfigured with processor-executable instructions to perform operationsfurther comprising: receiving the peripheral device originated callcontrol command via the first out of band link; and sending theperipheral device originated call control command to the mobile phonevia the first Bluetooth® link.
 46. The communication system of claim 44,wherein the peripheral device is a wireless personal hub, the first outof band link is a second Bluetooth® link, and the second out of bandlink is a third Bluetooth® link.
 47. The communication system of claim44, wherein: the first processor is configured with processor-executableinstructions to perform operations further comprising sending phonebookinformation to the peripheral device over the second out of band link;and the second processor is configured with processor-executableinstructions to perform operations further comprising receiving thephonebook information over the second out of band link.
 48. Thecommunication system of claim 39, wherein the communication device is aperipheral device, the communication system further comprising: an earpiece, comprising: a third transceiver; a third memory; and a thirdprocessor connected to the third transceiver and the third memory,wherein the second processor is configured with processor-executableinstructions to perform operations further comprising: establishing asecond Bluetooth® link with the ear piece, the second Bluetooth® linkincluding a call control connection and a second audio connectionbetween the ear piece and the peripheral device; and sending the mobilephone originated audio data to the ear piece via the second Bluetooth®link, and wherein the third processor is configured withprocessor-executable instructions to perform operations comprising:establishing the second Bluetooth® link with the peripheral device; andreceiving the mobile phone originated audio data via the secondBluetooth® link.
 49. The communication system of claim 48, wherein: thethird processor is configured with processor-executable instructions toperform operations further comprising sending ear piece originated callcontrol command and audio data to the peripheral device via the secondBluetooth® link; the second processor is configured withprocessor-executable instructions to perform operations furthercomprising: receiving ear piece originated call control command andaudio data from the ear piece via the second Bluetooth® link; andsending the ear piece originated call control command and audio data tothe mobile phone over the first audio connection over the firstBluetooth® link; and the first processor is configured withprocessor-executable instructions to perform operations furthercomprising receiving the ear piece originated call control command andaudio data via the first Bluetooth® link.
 50. The communication systemof claim 48, wherein the second processor is configured withprocessor-executable instructions to perform operations furthercomprising: modifying the mobile phone originated call control commandto generate a modified call control command; and combining the modifiedcall control command and the mobile phone originated audio data, andwherein the second processor is configured with processor-executableinstructions to perform operations such that sending the mobile phoneoriginated audio data to the ear piece via the second Bluetooth® linkcomprises sending the modified call control command and the mobile phoneoriginated audio data to the ear piece via the second Bluetooth® link.51. A communication system for providing call control information from amobile phone to a communication device, comprising: means forestablishing a first radio link between the mobile phone and thecommunication device; means for receiving a mobile phone originated callcontrol command and audio data from the mobile phone at thecommunication device via the first radio link; and means for separatingthe mobile phone originated call control command from the audio data atthe communication device.
 52. The communication system of claim 51,wherein the first radio link is a first Bluetooth® link including a callcontrol connection and a first audio connection.
 53. The communicationsystem of claim 52, wherein the communication device is an ear piece,the communication system further comprising: means for establishing afirst out of band link between the ear piece and a peripheral device;and means for sending the received mobile phone originated call controlcommand from the ear piece to the peripheral device via the first out ofband link.
 54. The communication system of claim 53, further comprising:means for receiving a peripheral device originated call control commandat the ear piece via the first out of band link; and means for sendingthe peripheral device originated call control command from the ear pieceto the mobile phone via the first Bluetooth® link.
 55. The communicationsystem of claim 54, wherein the first out of band link is a secondBluetooth® link.
 56. The communication system of claim 54, furthercomprising: means for establishing a second out of band link between themobile phone and the peripheral device; and means for sending phonebookinformation from the mobile phone to the peripheral device over thesecond out of band link.
 57. The communication system of claim 52,wherein the communication device is an ear piece, the communicationsystem further comprising: means for establishing a first out of bandlink between the ear piece and the mobile phone; means for establishinga second out of band link between the mobile phone and a peripheraldevice; means for sending the received mobile phone originated callcontrol command from the ear piece to the mobile phone via the first outof band link; means for receiving the mobile phone originated callcontrol command sent from the ear piece in a hub application resident onthe mobile phone; means for sending the mobile phone originated callcontrol command from the hub application to the peripheral device viathe second out of band link; and means for receiving the mobile phoneoriginated call control command sent from the hub application at theperipheral device.
 58. The communication system of claim 57, furthercomprising: means for receiving a peripheral device originated callcontrol command in the hub application resident on the mobile phone viathe second out of band link; means for sending the peripheral deviceoriginated call control command from the hub application to the earpiece via the first out of band link; means for receiving the peripheraldevice originated call control command at the ear piece via the firstout of band link; and means for sending the peripheral device originatedcall control command from the ear piece to the mobile phone via thefirst Bluetooth® link.
 59. The communication system of claim 57, whereinthe peripheral device is a wireless personal hub, the first out of bandlink is a second Bluetooth® link, and the second out of band link is athird Bluetooth® link.
 60. The communication system of claim 57, furthercomprising: means for sending phonebook information from the mobilephone to the peripheral device over the second out of band link.
 61. Thecommunication system of claim 52, wherein the communication device is aperipheral device, the communication system further comprising: meansfor establishing a second Bluetooth® link between the peripheral deviceand an ear piece, the second Bluetooth® link including a call controlconnection and a second audio connection between the ear piece and theperipheral device; and means for sending the mobile phone originatedaudio data from the peripheral device to the ear piece via the secondBluetooth® link.
 62. The communication system of claim 61, furthercomprising: means for receiving ear piece originated call controlcommand and audio data from the ear piece at the peripheral device viathe second Bluetooth® link; means for sending the ear piece originatedcall control command and audio data from the peripheral device to themobile phone over the first audio connection over the first Bluetooth®link; and means for receiving the ear piece originated call controlcommand and audio data at the mobile phone via the first Bluetooth®link.
 63. The communication system of claim 61, further comprising:means for modifying the mobile phone originated call control command atthe peripheral device to generate a modified call control command; andmeans for combining the modified call control command and the mobilephone originated audio data at the peripheral device, wherein means forsending the mobile phone originated audio data from the peripheraldevice to the ear piece via the second Bluetooth® link comprises meansfor sending the modified call control command and the mobile phoneoriginated audio data to the ear piece via the second Bluetooth® link.